[Mojang] Linus Cumselius
Assigned
Reported
Comments
Thanks for reporting this. I agree it is vague and it deserves a proper explanation and/or fix/change. I will open up an internal discussion about this immedately.
Is this still an issue?
Does this still happen? If so, please upload your launcher_log to this issue.
Ok, good. Thanks!
The log doesn't indicate any problems with connectivity, apart from not being able to connect to the auth service. Can you please double check your connectivity to https://authserver.mojang.com by pinging or trace routing or similar?
This is being worked on at the moment. Fix coming up soon. Sorry for any inconvinience this causes.
First of all, make sure you are not running the launcher already by rebooting you computer (or check in the activity manager).
Don't create a folder in %appdata%. That is taken cared of automatically.
If you would like to reinstall, please remove the .minecraft folder in %appdata% and the installation folder itself (wherever it was put originally) before trying again.
Alternatively you can just remove the "launcher_profiles.json" file and the ".version" file and then rerun the application. It should update to the latest version.
Please upload your launcher_profiles.json.
You can find it in your appdata folder. Write %appdata% in a "windows explorer" window and go into .minecraft folder.
Please update your graphics driver and try again.
This was a legit issue, albeit not launcher specific. It has since been fixed.
This issue is resolved in bootstrap versions 598 (MacOS) and 601 (Windows).
Also reported here:
This is a bootstrap fix that affects multiple core versions, the earliest, Windows version 2.1.5964.
As stated above, this issue is resolved in bootstrap versions 598 (MacOS) and 601 (Windows).
Let me just understand this correctly because the video show the launcher actually being run successfully.
The workaround mentioned above refers to the edit in the description?
The error shown in the log window (in the video) is likely caused by using a too new java version. Use Java 8 instead.
A bug fix containing a change as to where temp storage is located will be released within a reasonable timeframe. This should avoid the scenarios described above. Well, as long as that containing folder allows files to be run.
According to your logs, you should try any of these solutions:
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 335544320 bytes for Failed to commit pages from 655360 of length 81920
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
# Out of Memory Error (os_windows.cpp:3324), pid=3864, tid=9280
#
# JRE version: Java(TM) SE Runtime Environment (8.0_51-b16) (build 1.8.0_51-b16)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.51-b03 mixed mode windows-amd64 compressed oops)
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
Reading the provided log indicates that there's missing OpenGL support.
Please make sure you have OpenGL installed on your machine.
It seems the application is unable to create a gl surface (if what you provided above is actually the cef log). Please provide the complete launcher_cef_log.txt as well.
Things to try: make sure your graphics drivers are up to date or if you recently upgraded, that might be the reason you are suddenly seeing this, then please downgrade to the working driver version.
Let us know if this helped you or not.
See if the advice on this ticket might work: https://bugs.mojang.com/browse/MCL-12108
The things I'm describing now has been mentioned time and time before. Please try to keep this around for others to read.
When launcher says you are offline, it means the connection to the servers are failing at some point.
So the most likely causes are:
1) dns resolution fails, i.e authserver.mojang.com does not resolve to an actual ip adress.
2) dns resolution succeeds, but certificate checks fail
3) slow network (unlikely cause)
Solutions:
1) ensure nothing interferes with dns name resolution (for example modified hosts files on windows). In the logs similar to:
Notice the missing ip adress after "ip: ".
2) ensure logs does not contain stuff similiar to:
which indicates you may have some thirdparty "auth service" in between mojang auth services. Or some weird root certificate like in this case. Not good.
Historically there has been some other causes for this but they have all been adressed. Launcher defaults to ipv4 regardless of your own network protocol so if you still have problems and you know you are running ipv6, please file a bug and tell us.